Skip to content

OCPBUGS-102761: Use github.com/openshift-sustaining/net patch to fix CVE-2026-33814 - #1226

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.15from
Atharva-Shinde:4.15-CVE-2026-33814
Oct 13, 2026
Merged

OCPBUGS-102761: Use github.com/openshift-sustaining/net patch to fix CVE-2026-33814#1226
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.15from
Atharva-Shinde:4.15-CVE-2026-33814

Conversation

@Atharva-Shinde

@Atharva-Shinde Atharva-Shinde commented Sep 2, 2026

Copy link
Copy Markdown

Analysis / Root cause:

Solution description:

Replace golang.org/x/net with github.com/openshift-sustaining/net

Test setup:

Test cases:

Browser conformance:

  • Chrome
  • Firefox
  • Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

@Atharva-Shinde
Fix CVE-2026-33814
4092919 
Signed-off-by: Atharva Shinde <atshinde@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Sep 2, 2026
@openshift-merge-bot

openshift-merge-bot Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 2, 2026
@coderabbitai

coderabbitai Bot commented Sep 2, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: c2cca0f0-c1bb-48b6-b14e-8cb15d67bed1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 2, 2026
@openshift-ci-robot

openshift-ci-robot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

@Atharva-Shinde: This pull request references Jira Issue OCPBUGS-102761, which is invalid:

  • expected dependent Jira Issue OCPBUGS-102982 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Analysis / Root cause:

Solution description:

Replace golang.org/x/net with github.com/openshift-sustaining/net

Test setup:

Test cases:

Browser conformance:

  • Chrome
  • Firefox
  • Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
openshift-ci Bot requested review from jhadvig and spadgett September 2, 2026 12:47
@jhadvig

jhadvig commented Oct 5, 2026

Copy link
Copy Markdown
Member

/lgtm
/approve
/pipeline required
/label backport-risk-assessed
/verified by CI

@openshift-merge-bot

openshift-merge-bot Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-console
/test e2e-aws-operator
/test e2e-azure-ovn-upgrade
/test e2e-gcp-ovn

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 5, 2026
@jhadvig jhadvig added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 5, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 5, 2026
@openshift-ci-robot

openshift-ci-robot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

@jhadvig: This PR has been marked as verified by CI.

Details

In response to this:

/lgtm
/approve
/pipeline required
/label backport-risk-assessed
/verified by CI

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Oct 5, 2026
@openshift-merge-bot

openshift-merge-bot Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-console
/test e2e-aws-operator
/test e2e-azure-ovn-upgrade
/test e2e-gcp-ovn

@openshift-ci

openshift-ci Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Atharva-Shinde, jhadvig

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 5, 2026
@Atharva-Shinde

Atharva-Shinde commented Oct 8, 2026

Copy link
Copy Markdown
Author

/test e2e-aws-console

1 similar comment
@Atharva-Shinde

Atharva-Shinde commented Oct 12, 2026

Copy link
Copy Markdown
Author

/test e2e-aws-console

@jhadvig

jhadvig commented Oct 13, 2026

Copy link
Copy Markdown
Member

Overiding flaky frontend test
/override ci/prow/e2e-aws-console

@jhadvig

jhadvig commented Oct 13, 2026

Copy link
Copy Markdown
Member

/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 13, 2026
@openshift-ci

openshift-ci Bot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

@jhadvig: Overrode contexts on behalf of jhadvig: ci/prow/e2e-aws-console

Details

In response to this:

Overiding flaky frontend test
/override ci/prow/e2e-aws-console

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci

openshift-ci Bot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

@Atharva-Shinde: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-console 4092919 link true /test e2e-aws-console

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 5666a54 into openshift:release-4.15 Oct 13, 2026
9 checks passed
@openshift-ci-robot

openshift-ci-robot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

@Atharva-Shinde: Jira Issue Verification Checks: Jira Issue OCPBUGS-102761
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-102761 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Analysis / Root cause:

Solution description:

Replace golang.org/x/net with github.com/openshift-sustaining/net

Test setup:

Test cases:

Browser conformance:

  • Chrome
  • Firefox
  • Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-robot

openshift-merge-robot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Fix included in release 4.15.0-0.nightly-2026-10-14-171221

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jhadvig jhadvig Awaiting requested review from jhadvig
@spadgett spadgett Awaiting requested review from spadgett

Assignees

@jhadvig jhadvig

@sanketpathak sanketpathak

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@Atharva-Shinde @openshift-ci-robot @jhadvig @openshift-merge-robot @sanketpathak